More Pages: Addison Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26


The very classic
An excellent presentation of essential concepts
Yet another CS classicIt sets up a very formal framework for discussing alorithms, beginning at the beginning..an abstract mathematical model of a computer. and builds up the rest of the book using the model for implementation as well as quantification.
A solid framework for the analysis of algorithms is setup. The necessary mathematics is covered, helping in measuring an algorithm's complexity..basically the time and space complexities.
Then it goes on to deal with designing algorithms. the design methodology, with elaborate examples and exercises.
It should be admitted however that this is a solid text for the mathematically oriented. Thats the reason for the 5 stars!
If you want to go a little easy on the formalisms try
"Computer Algorithms, Pseudocode" by Ellis Horowitz, Sartaj Sahni, Sanguthevar Rajasekaran. I found it more pragmatic.


By far the most advanced C book I readIn one word, this book is the most advanced C book I've read, it presents lots of wonderful techniques and ideas, and more, all the things are very useful. For examples:
* Use standard C's setjmp/longjmp to implement WIn32 SEH-like exception handling machanism.
* Very detailed and smart memory management solution.
* All the data structures and utilities in well-defined, reusable format: atoms, tables, sets, vectors(dynamic arrays), rings, strings, arithmetric with any precisions, thread library... everything you need to build a whole new system.
I'd say that once you master each of those things (this means read and re-read until understanding occur, as Fransis Glassborow said ), you will be an outstanding programmer in any circumstance, and can be full of confidence to accept any programming challenge.
The only thing I complain is about the source code. The source code presenting style in this book is relative strange and difficult to catch. I tried to type the code into my PC, and found it's a unpleasent work. Fortunately, the all source can be download from the book's web page, so, I still gave 5 stars.
Excellent bookAs a programmer, I followed the way of C->C++->Java in the past three years. Now as I am coming back to C£¬ I find this book helps me to finish a cycle in software engineering.
When I am reading, I imagine how every idea introduced here can help to implement those "OOP" features of Java and C++. It reveals to me the very essence of software itself.
Originally I plan to buy it by company money, but now I changed the idea to pay by myself because I really want to keep it.
From novice to a professionalThe chapters provide source code which is clear, efficient, and outrightly professional, the description is concise, to the point and clear enough.Most of the code in the book can be used without any modification. I don't know of a book in the market that could teach how to design and implement a user-level threads library from the scratch WITHOUT any help from the Operating System. Simply wonderful


Excellent book with with tons of insightful knowledgeThe book is extremely well-organized and has tons of practical knowledge and insight. Furthermore, all the principles are illustrated using easy to follow, real life examples. Excellent throughout -- highly recommended!
Build Websites Anchored in Business RealityNick Flor, a Professor of Information Systems at Carnegie Mellon's Graduate School of Industrial Administration, argues that to create high-value business web sites requires business as well as technical knowledge. He draws a distinction between a mere web site, which he says, exchanges information and a business web site, which exchanges value - it generates significant revenues and/or drastically pares expenses.
He says three skills are required is proposed for systematically molding the Web to the specific requirements of the specific business.
1.General Business Knowledge.
2.An ability to analyze and diagnose business activities.
3.An ability to design Web treatments to address those activities.
To equip Web entrepreneurs and consultants with these requisite skills, Flor organizes his book into four sections:
1.Web Business 101 - This section covers the first business skill - the big picture. This general business primer includes a discussion of Return on Investment, Net Present Value, Payback, Internal Rate of Return, production, distribution and the effects of competition.
2.Web Business Engineering - Using the knowledge acquired in the first section, the book proposes a methodology that links technical knowledge with business specific knowledge.
3.Case Studies Putting Offline Activities Online
4.Case Studies Applying Web Business Engineering to Online Activities
Stick with the book until you reach the case studies. They add value to the first two sections.
This well-written book sheds important light on web development. By focusing on the author's definition of "value", managers and development teams will avoid aping successful online companies, building instead, systems that address what companies should be doing online based on their offline activities.
The way it should be done!The approach set forth in this incredible book is straightforward and focused solely on business imperatives. I suspect that the author and publisher realized that the title would attract IT professionals and consultants, which accounts for the inclusion of business 101. I almost skipped over this part and am glad I didn't. Even here what I thought I knew about business turned out to be superficial. The education you will receive in Business 101 goes well beyond the basics and I recommend that everyone read this regardless of whether you are an IT professional or have a business background. You might just discover that you've been misapplying common techniques such as NPV, IRR and ROI, or using the results in erroneous ways. In other words, the section titled "Business 101" is much, much more.
I loved the author's approach to value chain analysis, which is straightforward and based on a simple, but effective, notational language. Here, like in every other chapter, I learned techniques that will serve me well in general consulting assignments outside of web business engineering.
The web business engineering methodology itself is one of the leanest, most effective processes that I've ever encountered. I can only describe it as elegant. It's a blueprint for success when success is measured by how well a system is aligned to business strategy and goals. If you follow the method and resist the temptation to take shortcuts you will be rewarded with a system that meets all of your requirements and objectives whatever they may be - and you'll know exactly what the value of that system is to your organization.
A few observations about this book: (1) Give yourself plenty of time to read through this book and work through each example. It took me four times as long as it would for a book of approximate page count and topic complexity. If you're unwilling to make this commitment, perhaps you should pass this book up. (2) I fully agree with the author and a previous reviewer that web systems projects should be managed by business instead of IT. (3) If you're an IT professional get this book and read it from cover to cover - even if you never work on a web project you'll receive an incredible education in business factors and requirements analysis that will serve you well on *any* project. As a fellow IT professional I will assure you that this book will change your outlook.
This book is among the best I've read on any topic or subject and should be required reading for anyone who is assigned to a web project. It's also, in my opinion, one of the most important books published in the past few years.


Word differences
it's a great book!
It's really cool

A real eye opener. Wonderfully put together.I volunteer helping out homeless kids in Seattle, and from what I've seen this book does a good job of accurately protraying these children, including why they're on the street. He's unbiased and uncensored in his view, I think echo's review reflecting this (one of the kids followed in the book) only stands as a testament of this.
Definitely worth Buying!
Jim Goldberg got it right

An evocative, richly-textured collection.
At turns thought-provoking, touching and wonderfully weird.
Imaginative, creative, ideas you won't see anywhere elseAn extra plus is the authoress' personal journal; this should be a requirement in all books.


Miracle working pain relieving positions...
Back Pain Book
This is a really good, easy to understand book.

Good reference for L2TP!Clearly explains the tunnel and session negotiations with state machines and examples.
The implementation tips provides guidelines for implementing L2TP stack. Also explains the interaction of L2TP with PPP and IPSec and covers the security aspects of L2TP.
This book is more focussed on the L2TP client running in the ISP side(Compulsory L2TP tunneling).May be author can provide more details on the deployment where L2TP client running at the Remote User PC.
Well-written
well written

High-effective but fragileI was in OO development for five years and I was thinking about a solution which will improve the efficiency of OO design and help to avoid splitting the program between developers who create their own set of classes they are responsible for. Such splitting leads to integration problems and overall design imbalance. Fred Brooks has described this consequences in his famous book "The Mythical Man-Month", where the modules are being written first and integrated later, and the coordination of interfaces between modules written by each developer requires essential effort and time. The CRC Card Book shows how to have "the interfaces" coordinated in the very beginning.
However, the methodology described in this book is "fragile". As soon as it isn't followed by all of the developers, it became useless. But if it is followed, the results are amazing. The book, however, is not very easy to read and lack something which can attract the developers who are "neutral" to improving their way of creating OO programs. But, for the people who already have strong OO background and are seeking the way how to improve their efficiency significant, the book is a must-have.
Informal down to earth technique for everybodyThe technique itself can be very enjoyable and if you can convince very formal people to use it, it will change their lives, much more then any formal OO methodology will do. CRC Cards make you live software systems! This should be the first experience of everybody who wants to learn OO. You can even use it to explain your work to your kids:-)
Ideal for getting you started on "how to" identify Classes.A lot of OOA books like to tell how to design from start to finish. However, some (most) of us are thrown in some obligatory process without consent. CRC will bridge the gap on getting your Classes defined.
Also, CRC works well for "Use Cases". I use CRC after a good Use Case session for Class Diagrams. Some prefer to do CRC before Use Cases. That's the beauty, CRC can be injected anywhere you deem fit.
And, finally, this book will get you "thinking in objects" fast!


Fun readingRUSH is a fast moving adventure of three unlikely friends who find themselves mistakenly, but strategically involved in
supplying the U-boat submarines that were sinking Allied ships close to the shores of America in early part of World War II.
RUSH is a war story, action packed and often humorous. It moves to a surprising, dramatic and satisfactory end.
RUSH
A fast paced, compelling story
The two books are quite different in the language and formalism used: more formal and mathematical inclined AHU with respect to CLR. I'd say, the very classic style of his authors who have made history in the CS literature with their books (particularly 2 on algorithms and data structures, 2 on Computer Theory, 2 on Compilers, 1 on CS foundations): as these books have been used in most universities around the world for decades, they've proved to be real milestones in the education of thousands of students.
The books differ also in scope, since AHU is certainly not an encyclopedic collection as CLR does, with his roughly 500 pages against 1000. In spite of this, I'd point out the following: my textbook on Algorithms was CLR, but when we got to Complexity Classes (P-NP and theory behind) we "had" to switch to AHU for the simple reason that CLR did not almost mention at all Turing Machines nor Space Complexity, without which is certainly possible to learn e.g. about NP-TIME completeness, but without which, such a path would equally certainly miss some foundamental topics of Complexity Theory.
All in all, then, imo the book truly deserves 5 stars (and perhaps it would deserve a second, updated, edition too ... possibly, imho, through a bit less revolutionary revision job than they did with "Introduction to Automata Theory, Language and Computation").
As a final note, those looking for a more applicative and self-reference than an educational introductory text, could have a look at the two-volumes opera by the former Knuth's pupil, Robert Sedgewick (possibly the more consolidated C or C++ versions).